…ct commands

`inspect` -- and the dedicated `container inspect` / `image inspect` subcommands
-- declared `-f/--format` mirroring `docker inspect`, but parsed and then ignored
it: the full JSON array was always printed. Docker callers drive inspect with a
template and expect a bare scalar, e.g. dev stands and CI health gates:

    docker inspect -f '{{.State.Running}}' <container> | grep -q true

Against the unevaluated flag that grep is a coin-flip on the substring "true"
appearing somewhere in the JSON dump.

Add a small Go text/template evaluator (`GoTemplate`) for the `{{ .Dotted.Path }}`
field-access subset real inspect callers use, and route every inspect entry point
through a shared `InspectFormat` helper that renders `--format` (one line per
record) and otherwise prints the JSON exactly as before. This also wires
`--format` into `container inspect` and `image inspect`, which previously accepted
the flag for Docker surface parity but never applied it.

Behavior:
- Paths resolve against the Docker-shaped inspect JSON from us#40 (`.State.Running`,
  `.State.Status`, `.Id`, `.Name`, `.Config.Image`, `.NetworkSettings.IPAddress`,
  ...). Scalars render the Go way: bare `true`/`false`, integers without a decimal
  point, strings verbatim; an unknown/null path and array/object leaves render empty.
- Substitution is a single left-to-right pass by match range, so a resolved value
  that itself contains `{{...}}` is emitted verbatim and never re-triggers
  substitution.
- `--format json` is treated as Docker's documented special value (emit the JSON),
  not as a template.
- Any `{{...}}` block outside the supported field-access subset (`if`, `range`,
  `json`, `index`, a bare `{{.}}`, ...) throws rather than passing through as
  misleading literal text -- a silently-unevaluated template would feed false data
  to the grep/jq pipelines these outputs drive.

Add GoTemplateTests covering the dev-stand health-gate paths, integer-vs-bool
scalars (incl. Pid 0 on a stopped container), whitespace, multi-token / repeated
tokens, no cross-token / re-entrant substitution, array-leaf-empty, the
JSONSerialization bool->NSNumber bridging path, and fail-loud rejection of
unsupported actions.

…ct commands

`inspect` -- and the dedicated `container inspect` / `image inspect` subcommands
-- declared `-f/--format` mirroring `docker inspect`, but parsed and then ignored
it: the full JSON array was always printed. Docker callers drive inspect with a
template and expect a bare scalar, e.g. dev stands and CI health gates:

    docker inspect -f '{{.State.Running}}' <container> | grep -q true

Against the unevaluated flag that grep is a coin-flip on the substring "true"
appearing somewhere in the JSON dump.

Add a small Go text/template evaluator (`GoTemplate`) for the `{{ .Dotted.Path }}`
field-access subset real inspect callers use, and route every inspect entry point
through a shared `InspectFormat` helper that renders `--format` (one line per
record) and otherwise prints the JSON exactly as before. This also wires
`--format` into `container inspect` and `image inspect`, which previously accepted
the flag for Docker surface parity but never applied it.

Behavior:
- Paths resolve against the Docker-shaped inspect JSON from #40 (`.State.Running`,
  `.State.Status`, `.Id`, `.Name`, `.Config.Image`, `.NetworkSettings.IPAddress`,
  ...). Scalars render the Go way: bare `true`/`false`, integers without a decimal
  point, strings verbatim; an unknown/null path and array/object leaves render empty.
- Substitution is a single left-to-right pass by match range, so a resolved value
  that itself contains `{{...}}` is emitted verbatim and never re-triggers
  substitution.
- `--format json` is treated as Docker's documented special value (emit the JSON),
  not as a template.
- Any `{{...}}` block outside the supported field-access subset (`if`, `range`,
  `json`, `index`, a bare `{{.}}`, ...) throws rather than passing through as
  misleading literal text -- a silently-unevaluated template would feed false data
  to the grep/jq pipelines these outputs drive.

Add GoTemplateTests covering the dev-stand health-gate paths, integer-vs-bool
scalars (incl. Pid 0 on a stopped container), whitespace, multi-token / repeated
tokens, no cross-token / re-entrant substitution, array-leaf-empty, the
JSONSerialization bool->NSNumber bridging path, and fail-loud rejection of
unsupported actions.